Allow multiple content types and schemas (via oneOf) according to OpenAPI 3.0 spec #792
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… and schemas (via oneOf) according to OpenAPI 3.0 spec
shalvah
changed the title
|
Completed this, added a test. Although I think it only supports multiple schemas. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR brings the generator in line with the OpenAPI 3.0 Spec (according to https://swagger.io/docs/specification/describing-responses/) and implements multiple response content types and support for multiple response schemas in a single content type (via oneOf).
Currently missing a Unit test for this behavior (will add this soon).
I couldn't find this specific info anywhere in the documentation so I think there is no change necessary.
As I'm not familiar with Postman I don't know if any change is necessary there.